OpenEdge Development:<br />Progress Dynamics Administration Mapping lookup fields to SDO fields through viewer widgets

For the CustomerCodeLookup example created on customer_obj, you can fix the redundancy for the user created by linking the lookup fields directly to the SDO by permanently hiding the customer_name fill-in object used to map the lookup display field to the corresponding SDO field. However, you might prefer to map lookup fields through separate viewer widgets mapped to the SDO.

Ensure that you have created a join from art_order to arm_customer in the art_order SDO (artorfullo) and added the following fields for the lookup from arm_customer to the SDO:

customer_balance

customer_code

customer_name

For more information, see the "Preparing the lookup for field mapping" section.

After you have saved the updated SDO, open the art_order viewer (artorviewv) in the AppBuilder.

Add a new fill-in widget, fiCustCode, to the viewer, formatted to display arm_customer.customer_code.

Note: This example assumes that you have already added the fiCustBalance widget as part of creating CustomerCodeLookup in the tutorial. For more information, see OpenEdge Development: Progress Dynamics Getting Started .

Right-click on the CustomerCodeLookup and choose Instance Properties from the pop-up menu. This displays the SmartDataField Maintenance (Instance Properties) window.

In the query field browser, select the row for arm_customer.customer_code and type the following column values:

Link field — YES.

Linked widget — fiCustCode.

This is SmartDataField Maintenance (Instance Properties) as it appears after you have set these column values:

Note: The corresponding column values for the arm_customer.customer_balance row have already been set from the tutorial.

Choose the Map Fields tab. The left selection list on this tab lists all the fields in the data source (artorfullo SDO), and the right selection list lists the linked viewer fields (fiCustBalance and fiCustCode) for the lookup query.

Map these viewer fields to the corresponding SDO fields:

Select the arm_customer.customer_balance field in the left selection list and the fiCustBalance field in the right selection list. The Map button now becomes enabled, as shown:

Choose the Map button. The two selected fields disappear from the selection lists and appear in the Mapped fields editor.

Repeat Step a and Step b for the arm_customer.customer_code field in the left selection list and the fiCustCode field in the right selection list.

Map the Displayed field for the lookup:

Select the arm_customer.customer_name field from the left selection list and <Displayed Field> from the right selection list.

Choose the Map button.

The entire field mapping for the lookup appears in the Mapped field editor, as shown:

Save the instance properties to complete the dynamic lookup field mapping.

The field redundancy that the first mapping option creates for this example (see the "Linking lookup fields directly to SDO fields on the viewer" section) does not occur using this option. The Map Fields tab allows you to specify the mapping of the lookup Displayed field to the corresponding SDO field without the need for a linked viewer widget that would otherwise create a redundant field on the viewer mapped to the SDO that displays the same value. Although this mapping option requires more steps to set up, it has the flexibility to accommodate field mappings for any lookup, no matter how it is defined.